Multiple Prefix Connections with Translated Virtual Local Area Network

ABSTRACT

A system comprising an access node (AN) coupled to a plurality of service providers (SPs) and a host and configured to forward a plurality of services between the SPs and the host using a plurality of first connections between the AN and the host and a plurality of second connections between the AN and the SPs, and a router gateway (RG) positioned between the host and the AN and coupled to the AN via an access line that comprises the first connections, wherein the AN translates a plurality of first identifiers for the first connections to a plurality of second identifiers for the second connections to route the services appropriately between the host and the SPs over the first connections and the corresponding second connections.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims priority to U.S. Provisional PatentApplication No. 61/178,107 filed May 14, 2009 by John Kaippallimalil andentitled “System and Method for Supporting Multiple Prefix Connectionswith User Defined Virtual Local Area Networks (VLANs) in aCommunications System”, which is incorporated herein by reference as ifreproduced in its entirety.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not applicable.

REFERENCE TO A MICROFICHE APPENDIX

Not applicable.

BACKGROUND

In some networks, a residential gateway (RG) or a host (e.g. asubscriber) can be connected to multiple service providers (SPs) via anaccess node (AN) and over a shared interface or access line, such as anactive line access (ALA). Each service provider can provide one ormultiple services to the host via the shared interface or access line.Typically, the services are routed between the host and the appropriateSPs by the AN over the access line based on a plurality of sourceInternet Protocol (IP) addresses or prefixes that can be obtained fromthe SPs. As such, the AN may need to process the service packets toobtain the IP addresses or prefixes from the packets' headers. However,the AN cannot use the IP addresses or prefixes to send routersolicitation (RS) messages, Dynamic Host Configuration Protocol (DHCP)messages, or other messages from the host that are sent prior toobtaining the IP addresses or prefixes from the SPs.

SUMMARY

In one embodiment, the disclosure includes a system comprising an ANcoupled to a plurality of SPs and a host and configured to forward aplurality of services between the SPs and the host using a plurality offirst connections between the AN and the host and a plurality of secondconnections between the AN and the SPs, and a RG positioned between thehost and the AN and coupled to the AN via an access line that comprisesthe first connections, wherein the AN translates a plurality of firstidentifiers for the first connections to a plurality of secondidentifiers for the second connections to route the servicesappropriately between the host and the SPs over the first connectionsand the corresponding second connections.

In another embodiment, the disclosure includes a network componentcomprising at least one processor configured to implement a methodcomprising receiving a packet for a service on a connection between asubscriber and a SP, replacing a Virtual Local Area Network (VLAN) tagfor the subscriber in the packet with a Customer VLAN (C-VLAN)/ServiceVLAN (S-VLAN) tag for the subscriber and the SP that matches a MediaAccess Control (MAC) address for a RG in the packet if the packet isreceived from the RG, and replacing a C-VLAN/S-VLAN tag for thesubscriber and the SP in the packet with a VLAN tag for the subscriberthat matches the MAC address for the RG in the packet if the packet isreceived from the SP.

In yet another embodiment, the disclosure includes a method comprisingreceiving from a host an authentication request for a VLAN connection tothe host, receiving a C-VLAN/S-VLAN label for the host and a SP uponauthentication of the VLAN, and associating the VLAN and theC-VLAN/S-VLAN label with a MAC address of a RG between the host and theSP.

These and other features will be more clearly understood from thefollowing detailed description taken in conjunction with theaccompanying drawings and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of this disclosure, reference is nowmade to the following brief description, taken in connection with theaccompanying drawings and detailed description, wherein like referencenumerals represent like parts.

FIG. 1 is a schematic diagram of an embodiment of an access networksystem.

FIG. 2 is a protocol diagram of an embodiment of a VLAN registrationmethod.

FIG. 3 is a schematic diagram of an embodiment of a VLAN identificationlist.

FIG. 4 is a schematic diagram of an embodiment of a VLAN associationlist.

FIG. 5 is a schematic diagram of an embodiment of a VLAN translationlist.

FIG. 6 is a schematic diagram of an embodiment of a general-purposecomputer system.

DETAILED DESCRIPTION

It should be understood at the outset that although an illustrativeimplementation of one or more embodiments are provided below, thedisclosed systems and/or methods may be implemented using any number oftechniques, whether currently known or in existence. The disclosureshould in no way be limited to the illustrative implementations,drawings, and techniques illustrated below, including the exemplarydesigns and implementations illustrated and described herein, but may bemodified within the scope of the appended claims along with their fullscope of equivalents.

Disclosed herein is a system and method for identifying a plurality ofconnections over a shared access line (e.g. ALA) between a RG or a host,such as a subscriber, and a plurality SPs. The connections maycorrespond to a plurality of services that may be provided to aplurality of hosts or subscribers coupled to the RG, by a plurality ofSPs. Each SP may provide one or multiple services to the host, which maybe routed or forwarded by an AN via the access line. The services may beforwarded by identifying each connection, e.g. between a host and a SP,and hence sending each service over the corresponding connection. Eachservice connection between the RG and the AN may be identified using aMAC address for the RG and a VLAN ID that identifies the subscriber.Each corresponding service connection between the AN and the SP may beidentified by the MAC address of the RG, a C-VLAN ID that identifies thesubscriber, and a S-VLAN ID that identifies the SP. Such combinations ofidentifiers may be maintained by the AN. As such, the AN may forwardservice traffic appropriately between the hosts and the SPs over thecorresponding connections by translating the MAC address and VLAN ID tothe corresponding MAC address, and corresponding C-VLAN ID and S-VLANID, and vice-versa. The VLAN identification and translation may be usedto route the different services between the hosts and SPs over theaccess line without the knowledge of or using specified source prefixesor IP addresses and without processing the packets to obtain theprefixes or IP addresses, e.g. in the packets' headers.

FIG. 1 illustrates an embodiment of an access network system 100. Theaccess network system 100 may comprise at least one host 110, a RG 120,an AN 130, an access network 140, a first SP (SP1) 142, and a second SP(SP2) 144. Each host 110 may be coupled to the RG 120, for instance at acustomer premise or a local network. The AN 130 and the access network140 may correspond to an access network provider (ANP) and may becoupled to each other and to the RG 120 via an access line 190, as shownin FIG. 1. The AN 130 may also be coupled to each of the first SP 142and the second SP 144. The first SP 142 may comprise a first accessrouter (AR; AR1) 152 that may be coupled to the AN 130 and a first SPnetwork (SPN; SPN1) 162 that may be coupled to the first AR 152.Similarly, the second SP 144 may comprise a second AR (AR2) 154 that maybe coupled to the AN 130 and a second SPN (SPN2) 164 that may be coupledto the second AR 154. Although three hosts (e.g. H1, H2, and H3) and twoSPs (e.g. SP1 and SP2) are shown in FIG. 1, the access network system100 may comprise any number of hosts and SPs. Other embodiments of theaccess network system 100 may comprise a host 110 or a plurality ofhosts 110 that may be coupled to the AN 130 without using the RG 120. Inother embodiments, a plurality of RGs 120 may be coupled to the AN 130via a plurality of corresponding access lines 190. However, in all suchembodiments, the access line 190 may carry traffic or services between aplurality of SPs and any host 110, e.g. via the RG 120. Further, thedifferent services may be provided to the hosts 110 over the access line190 via different connections (e.g. VLANs), which is represented by thedifferent line patterns in FIG. 1.

The host 110 may be any user equipment (UE) or device configured fortransmitting and/or receiving signals to and from the RG 120, such aselectrical or optical signals. In one embodiment, the host 110 maycreate, send, or receive the signals using a fixed link, such as a wiredcable or a fiber optic cable, between the host 110 and the RG 120. Thefixed link may implement Ethernet, Asynchronous Transfer Mode (ATM), IP,or any other suitable protocol. The host 110 may be a fixed device,including a personal computer (PC) such as a desktop computer, atelephone such as a voice over IP (VoIP) telephone, or a set top box.Alternatively, the host 110 may be a portable device, such as a laptopcomputer, or a cordless phone, which may use the fixed link tocommunicate with the RG 120. In another embodiment, the host 110 may beany user mobile device, component, or apparatus that communicates withthe RG 120 using a wireless link. For example, the host 110 may be amobile phone, a personal digital assistant (PDA), a portable computer,or any other wireless device. As such, the host 110 may comprise aninfrared port, a BLUETOOTH interface, an Institute of Electrical andElectronics Engineers (IEEE) 802.11 compliant wireless interface, or anyother wireless communication system that enables the host 110 tocommunicate wirelessly with the RG 120. Accordingly, the wireless linkmay be an IEEE 802.11 link, a Wi-Fi link, a BLUETOOTH link, a WorldwideInteroperability for Microwave Access (WiMAX) link, a near fieldcommunication (NFC) link, an Infrared Data Association (IrDa) link, orany other communication link established using wireless technology.

The RG 120 may be any device or component configured to allow the host110 to gain access to the access network 140 associated with the AN 130.For instance, the RG 120 may be configured to establish a wireless orfixed link with the host 110 and forward communications between the host110 and the AN 130. For example, the RG 120 may be an IP router, such asa customer premises equipment (CPE) router or any router equipmentlocated at a subscriber's premises and that communicates with the accessnetwork. Alternatively, the RG 120 may comprise a digital subscriberline (DSL) modem, a cable modem, or a set-top box. In yet anotherembodiment, the RG 120 may be a node that forwards IPv4 and/or IPv6packets to and from the host 110. Further, the RG 120 may be a routedRG, which may establish authentication with the access network and allowa trusted host 110 to communicate with the access network.

The AN 130 may be any device that transports communications between theRG 120 and the first SP 142 and between the RG 120 and the second SP144. For example, the AN 130 may be a switch, a router, or a bridge,such as a Provider Edge Bridge (PEB) or a Provider Core Bridge (PCB).The AN 130 may be coupled to each of the first SP 142 and the second SP144 via fixed links, such as Ethernet or IP links. The AN 130 mayreceive different service traffic from the first SPN 162 via the firstAR 152, the second SPN 164 via the second AR 154, or both and forwardthe different service traffic to the RG 120 via the access network 140.The AN 130 may receive/send the different service traffic from/to thefirst SP 142 and the second SP 144 via different connections, which mayinclude a C-VLAN, a priority tagged VLAN, an S-VLAN, or combinationsthereof. The different service traffic may also be forwarded between theAN 130 and the RG 120 using different virtual connections, such asdifferent VLANs, over the shared access line 190. The access line 190may be a fixed link between the AN 130 and the RG 120, such as a wiredcable or a fiber optic cable. The different service connections on bothsides of the AN 130 are represented by the different line patterns inFIG. 1.

The first SPN 142 and the second SPN 144 may comprise different orsimilar SPs, such as an Internet service provider (ISP), a networkservice provider (NSP), an application service provider (ASP), orcombinations thereof. The first SPN 162 and the second SPN 164 may eachprovide at least one service to the host 110 via the first AR 152 andthe second AR 154, respectively. For example, the first SPN 162 and/orthe second SPN 164 may provide IP Television (TV) services, which may bestreamed down to the hosts 110 over the access line 190.

The first AR 152 and the second AR 154 may be any device that forwardspackets between the AN 130 and each of the first SPN 162 and the secondSPN 164, respectively. The packets may be forwarded between the AN 130and each of the first SPN 162 and the second SPN 164 using fixed links.For example, the first AR 152, and similarly the second AR 154, maycomprise any of a Broadband Routed Access Servers (BRAS), a Cable ModemTermination Server (CMTS), a router, or combinations thereof. Forinstance, the first AR 152 and/or the second AR 154 may comprise aBackbone Edge Bridge (BEB), a PEB, a PCB, or a user network interfaces(UNI). In some embodiments, the first AR 152 or the second AR 154 may bea point-oriented wire-line node, such as a DSL connection or a providernetwork edge device.

In some embodiments, the first AR 152 and the second AR 154 may alsoprovide a plurality of network access services to the host 110 at thecustomer premise. For instance, the first AR 152 and/or the second AR154 may exchange authentication information with the access networkusing the IEEE 802.1X protocol and with an authentication server, suchas an authentication, authorization, and accounting (AAA) server toauthenticate the host 110 or the RG 120. The authentication informationmay be exchanged using a remote authentication protocol, such as aRemote Authentication Dial In User Service (RADIUS) protocol or aDiameter protocol. Further, the first AR 152 and/or the second AR 154may provide quality of service (QoS) requirements for downstreamcommunications with the hosts 110.

In an embodiment, the different services communicated over the differentconnections between the RG 120 and the AN 130 may be identified byassociating the MAC address of the RG 120 with the VLAN IDs for thedifferent hosts 110 or subscribers per host 110. Since the MAC addressidentifies the RG 120 and the VLAN IDs identify the individualsubscribers, the combinations of MAC address and VLAN IDs may be used toidentify the individual services and connections for the different hosts110. In some embodiments, the hosts' prefixes or addresses (e.g. IPprefixes or addresses) may also be combined with the RG MAC address andcorresponding VLAN IDs to identify and distinguish the differentservices over the different connections to the hosts 110. The AN 130 maymaintain the RG MAC address, the VLAN IDs, and optionally the prefixesin a VLAN identification list or table. The AN 130 may also associatethe RG MAC address and the VLAN IDs with a port or interface for theaccess line 190, e.g. for each RG 120 coupled to the AN 130. Forinstance, the AN 130 may maintain the MAC address for each RG 120, theVLAN IDs, and the port ID in a VLAN association list or table.

Additionally, the different services may be associated with thecorresponding subscribers and SPs, e.g. the first SP 142 and the secondSP 144, using a plurality of C-VLAN IDs that correspond to thesubscribers and S-VLAN IDs that correspond to the SPs. The C-VLAN ID andS-VLAN ID pairs may also be associated with the RG MAC address. The AN130 may maintain the RG MAC address, the C-VLAN IDs, and the S-VLAN IDsin a VLAN translation list or table. The AN 130 may use the associationbetween the RG MAC address, the C-VLAN IDs, and the S-VLAN IDs toproperly route the services that correspond to the hosts 110 to and fromthe SPs. Specifically, the AN 130 may translate the RG MAC address andVLAN IDs in the packets received from the RG 120 over the access line190 into the RG MAC address and corresponding C-VLAN ID and S-VLAN IDpairs, and thus forward the packets to the corresponding SPs over theappropriate links. Similarly, the AN 130 may translate the RG MACaddress and C-VLAN ID/S-VLAN ID in the packets received from the SPs(e.g. in Q-in-Q labels in the packets) into the RG MAC address andcorresponding VLAN ID, and thus forward the packets to the RG 120 overthe access line 190. The RG 120 may send the packets received from theAN 130 over the access line 190 based on the RG MAC address and VLAN ID.

The AN 120 may use such VLAN identification and translation scheme toroute service related traffic, such as solicitation messages and/or DHCPrequests, over the access line 190 without the knowledge of host IPaddresses or prefixes, e.g. before the SPs assign the IP addresses orprefixes to the hosts 110. The VLAN identification and translationscheme may also be used to route service messages, e.g. DHCP or IPv6Neighbor Discovery messages, using unspecified IP addresses or prefixes.For instance, the services may be forwarded over the correspondingconnections without the need to process the IP addresses or prefixes,e.g. in the service packets' headers. As such, the VLAN identificationand translation scheme may be implemented at the network link layer,e.g. using Ethernet protocols, which may improve transfer efficiency,reduce processing complexity, or both.

In an embodiment, the RG 120 and/or the host 110 may initially send anauthentication request for a new VLAN connection for each of the firstSP 142 and the second SP 144. When the AN 130 receives on its port anauthentication request for a new VLAN connection from the RG 120 or thehost 110, the AN 130 may initiate an AAA authentication sequence or anyother authentication sequence to authenticate the host 110. Theauthentication request may be received on the port coupled to the accessline 190 between the RG 120 and the AN 130. After authentication iscompleted, the RG 120 and/or the host 110 may establish a VLANconnection for each of the first SP 142 and the second 144 to receivethe services. The host 110 may be configured to send/receive the servicepackets using the authenticated VLAN connection or a second VLAN, e.g.between the host 110 and the RG 120. In another embodiment, the VLANconnections may be configured before initiating the service sessions,where the RG 120 may be configured to use a plurality of VLANs orC-VLANs for each SP to obtain services from that SP. Additionally, theRG 120 or the host 110 may obtain a prefix using a RS/routingacknowledgement (RA) sequence, an address using DHCP, or a delegatedprefix for each host 110. Alternatively, the RG 120 may obtain adelegated prefix but not the host 110, e.g. as specified in InternetEngineering Task Force (IETF) Request for Comments (RFC) 3633. Theprefix, address, or delegated prefix may be associated with thecorresponding VLAN connection, e.g. in the VLAN identification list.

Upon provisioning or configuring the VLAN connection, the AN 130 maystore the RG MAC address, the VLAN ID for the subscriber, and an accessinterface or port ID, e.g. in the VLAN association list. The AN 130 mayalso store the authentication lifetime for the subscriber and any otherinformation about the RG 120 and/or the host 110. Additionally, the AN130 may obtain from the AAA entity (or an authentication server) aC-VLAN/S-VLAN pair for each indicated VLAN in the authentication signaland store it with the corresponding VLAN, e.g. in the VLAN translationlist. Alternatively, the C-VLAN/S-VLAN pair may be configured staticallyfor each VLAN.

FIG. 2 illustrates an embodiment of a VLAN registration method 200,which may enable an AN to route different services for a plurality ofSPs between the SPs and a RG or a host over an access line. For example,the VLAN registration method 200 may be implemented, e.g. by the AN 130and/or the RG 120, to properly forward the different service trafficbetween the hosts 110 and any of the first SP 142 and the second SP 144over the appropriate connections and the channel 190. At step 201, theRG and/or host may boot up and establish a VLAN connection for any SP(e.g. VLAN 1 for SP1 or VLAN 2 for SP2), for instance based onconfiguration information by the network or the operator.

At step 202, the RG may authenticate the VLAN connection with acorresponding SP via the AN and the AR of the SP, e.g. AR1 for SP1 orAR2 for SP2. Accordingly, the RG may send to the AN a IEEE 802.1X,protocol for carrying authentication for network access (PANA), or otherauthentication signal with a network access identifier (NAI) thatincludes a suffix with the domain name of the service provider (SP). TheAN may receive the authentication signals for the VLANs for a pluralityof SPs and store the associations between the VLANs and the SPs. Forexample, the AN may associate VLAN 1 with SP1 and VLAN2 with SP2 andregister the corresponding entries in the VLAN association list. The ANmay then request from an AAA server or other authentication entity (notshown) to authenticate the RG or host. In reply, the AAA mayauthenticate the RG or host and send back an authentication status“success” to the AN. The AAA server may also provide the AN aC-VLAN/S-VLAN pair, e.g. as a VLAN Q-in-Q label, for the authenticatedVLAN, which may be stored at the AN. The AN may then forward theauthentication status “success” to the RG over the corresponding VLAN.

At step 203, the RG may initiate a RS/RA exchange via the AN with the ARthat corresponds to the SP, e.g. after configuring the link-localaddress. The RS/RA request may be initiated to obtain routerinformation, such as an advertised prefix, an authentication lifetime,and/or other information. The RS/RA exchange messages may indicate thecorresponding VLAN, e.g. VLAN 1 for SP1, but may not specify a source IPaddress or may comprise an unspecified IP address. Alternatively, the RGmay be a requesting router, e.g. according to RFC 3633, that sends tothe AR a DHCP request to obtain an Identity Association for PrefixDelegation (IA_PD). If the RG does not have an IP address, the DHCPrequest may be sent with an unspecified IP address and the correspondingVLAN ID, e.g. VLAN 1 for AR1 and SP1.

At step 204, the host associated with the VLAN connection, e.g. H1, mayinitiate a RS/RA message sequence with the RG to request an IP prefix oraddress. The RG may determine which pool of delegated prefixes to use toprovide an IP prefix (e.g. IPv6 prefix) to the host based on staticconfiguration and/or policies. The RG may send then IP prefix to thehost and associate the corresponding VLAN, e.g. VLAN 1 for H1, to theSP.

At step 205, the RG and the AN may forward the service packets using theVLAN connection, e.g. VLAN 1, between the corresponding host and AR,e.g. H1 and AR1. The AR may translate the VLAN in the packets bysubstituting the VLAN in the packet header with a corresponding Q-in-Qlabel (e.g. C-VLAN/S-VLAN pair) when the packet is sent from the host tothe SP. The AN may also substitute the Q-in-Q label in the packet headerwith a corresponding VLAN ID when the packet is sent from the SP to thehost.

FIG. 3 illustrates an embodiment of a VLAN identification list 300,which may be used to identify the RG MAC address with the VLANconnections to each subscriber and the host prefixes, for instance atthe AN. The RG MAC address in the VLAN identification list 300 may beassociated with each host prefix and a VLAN for each subscriber. Forinstance, the VLAN identification list 300 may be stored at the AN inthe form of a table, which may comprise a host prefix column 302, a RGMAC address column 306, and a VLAN column 308. The host prefix column302 may comprise the individual prefixes assigned to the differenthosts. The RG MAC address column 306 may comprise the MAC address of aRG coupled to the AN. The VLAN column 308 may comprise the VLAN ID foreach connection to a host or subscriber. Additionally, the VLANidentification list 300 may comprise a prefix length column 304 thatindicates the length of each assigned prefix, e.g. in bits. For example,the prefix length may be equal to about 64 bits in the case of IPv6assigned prefixes or about 32 bits for IPv4 assigned prefixes.

The VLAN association list and the VLAN translation list together maymake up the mapping from RG-AN segment to AN-SP segment. FIG. 4illustrates an embodiment of a VLAN association list 400, which may beused to associate the RG MAC address with the VLAN connections to eachsubscriber and the access line connection port on the AN. The RG MACaddress in the VLAN association list 400 may be associated with the portID of the access line and a VLAN for each subscriber. For instance, theVLAN association list 400 may be stored at the AN in the form of atable, which may comprise a RG MAC address column 402, a VLAN ID column404, and a port column 406. The RG MAC address column 402 may comprisethe MAC addresses for a RG coupled to the AN. The VLAN column 404 maycomprise the VLAN ID for each subscriber or host. The port column 406may comprise the port ID associated with all the VLANs for the sameaccess line and RG. However, if multiple RGs and corresponding accesslines are coupled to the AN, the RG MAC address column 402 may comprisea plurality of RG MAC addresses and the port column 406 may comprise aplurality of port IDs.

FIG. 5 illustrates an embodiment of a VLAN translation list 500, whichmay be used to translate the VLANs associated with the RG MAC address,e.g. to switch between the VLAN tags that identify the connectionsbetween the AN and the RG over the access line and the C-VLAN/S-VLANlabels that identify the connections between the AN and the differentSPs. The RG MAC address in the VLAN translation list 500 may beassociated with a C-VLAN for each subscriber or host, a S-VLAN for eachSP, and optionally a SP ID or domain name, which may be stored at the ANin the form of a table. As such, the VLAN translation list 500 maycomprise a RG MAC address column 502, a C-VLAN column 504, a S-VLANcolumn 506, and optionally a SP column 508. The RG MAC address column502 may comprise the MAC address of the RG. The C-VLAN column 504 maycomprise the C-VLAN ID for each subscriber or host. The S-VLAN column506 may comprise the S-VLAN ID for each SP. Similarly, the SP column 508may comprise a SP ID or domain name for each SP. The AN may use theC-VLAN/S-VLAN associations with the RG MAC address in the VLANtranslation list 500 and the VLAN associations with the same RG MACaddress in the VLAN association list 400 to translate the VLANs betweenthe hosts and the SPs.

The network components described above may be implemented on anygeneral-purpose network component, such as a computer or networkcomponent with sufficient processing power, memory resources, andnetwork throughput capability to handle the necessary workload placedupon it. FIG. 6 illustrates a typical, general-purpose network component600 suitable for implementing one or more embodiments of the componentsdisclosed herein. The network component 600 includes a processor 602(which may be referred to as a central processor unit or CPU) that is incommunication with memory devices including secondary storage 604, readonly memory (ROM) 606, random access memory (RAM) 608, input/output(I/O) devices 610, and network connectivity devices 612. The processor602 may be implemented as one or more CPU chips, or may be part of oneor more application specific integrated circuits (ASICs).

The secondary storage 604 is typically comprised of one or more diskdrives or tape drives and is used for non-volatile storage of data andas an over-flow data storage device if RAM 608 is not large enough tohold all working data. Secondary storage 604 may be used to storeprograms that are loaded into RAM 608 when such programs are selectedfor execution. The ROM 606 is used to store instructions and perhapsdata that are read during program execution. ROM 606 is a non-volatilememory device that typically has a small memory capacity relative to thelarger memory capacity of secondary storage 604. The RAM 608 is used tostore volatile data and perhaps to store instructions. Access to bothROM 606 and RAM 608 is typically faster than to secondary storage 604.

At least one embodiment is disclosed and variations, combinations,and/or modifications of the embodiment(s) and/or features of theembodiment(s) made by a person having ordinary skill in the art arewithin the scope of the disclosure. Alternative embodiments that resultfrom combining, integrating, and/or omitting features of theembodiment(s) are also within the scope of the disclosure. Wherenumerical ranges or limitations are expressly stated, such expressranges or limitations should be understood to include iterative rangesor limitations of like magnitude falling within the expressly statedranges or limitations (e.g., from about 1 to about 10 includes, 2, 3, 4,etc.; greater than 0.10 includes 0.11, 0.12, 0.6, etc.). For example,whenever a numerical range with a lower limit, R₁, and an upper limit,R_(u), is disclosed, any number falling within the range is specificallydisclosed. In particular, the following numbers within the range arespecifically disclosed: R=R₁+k*(R_(u)-R₁), wherein k is a variableranging from 1 percent to 100 percent with a 1 percent increment, i.e.,k is 1 percent, 2 percent, 3 percent, 4 percent, 5 percent, . . . , 50percent, 51 percent, 52 percent, . . . , 95 percent, 96 percent, 97percent, 98 percent, 99 percent, or 100 percent. Moreover, any numericalrange defined by two R numbers as defined in the above is alsospecifically disclosed. Use of the term “optionally” with respect to anyelement of a claim means that the element is required, or alternatively,the element is not required, both alternatives being within the scope ofthe claim. Use of broader terms such as comprises, includes, and havingshould be understood to provide support for narrower terms such asconsisting of, consisting essentially of, and comprised substantiallyof. Accordingly, the scope of protection is not limited by thedescription set out above but is defined by the claims that follow, thatscope including all equivalents of the subject matter of the claims.Each and every claim is incorporated as further disclosure into thespecification and the claims are embodiment(s) of the presentdisclosure. The discussion of a reference in the disclosure is not anadmission that it is prior art, especially any reference that has apublication date after the priority date of this application. Thedisclosure of all patents, patent applications, and publications citedin the disclosure are hereby incorporated by reference, to the extentthat they provide exemplary, procedural, or other details supplementaryto the disclosure.

While several embodiments have been provided in the present disclosure,it should be understood that the disclosed systems and methods might beembodied in many other specific forms without departing from the spiritor scope of the present disclosure. The present examples are to beconsidered as illustrative and not restrictive, and the intention is notto be limited to the details given herein. For example, the variouselements or components may be combined or integrated in another systemor certain features may be omitted, or not implemented.

In addition, techniques, systems, subsystems, and methods described andillustrated in the various embodiments as discrete or separate may becombined or integrated with other systems, modules, techniques, ormethods without departing from the scope of the present disclosure.Other items shown or discussed as coupled or directly coupled orcommunicating with each other may be indirectly coupled or communicatingthrough some interface, device, or intermediate component whetherelectrically, mechanically, or otherwise. Other examples of changes,substitutions, and alterations are ascertainable by one skilled in theart and could be made without departing from the spirit and scopedisclosed herein.

1. A system comprising: an access node (AN) coupled to a plurality ofservice providers (SPs) and a host and configured to forward a pluralityof services between the SPs and the host using a plurality of firstconnections between the AN and the host and a plurality of secondconnections between the AN and the SPs, and a router gateway (RG)positioned between the host and the AN and coupled to the AN via anaccess line that comprises the first connections, wherein the ANtranslates a plurality of first identifiers for the first connections toa plurality of second identifiers for the second connections to routethe services appropriately between the host and the SPs over the firstconnections and the corresponding second connections.
 2. The system ofclaim 1, wherein the RG is coupled to a plurality of hosts that eachreceives a service from one of the SPs over one of the firstconnections.
 3. The system of claim 2, wherein each of the firstidentifiers comprises a Media Access Control (MAC) address for the RG, aVirtual Local Area Network (VLAN) identifier (ID) that corresponds toone of the hosts, and a host prefix that identifies the host, andwherein the first identifiers are maintained in a first list at the AN.4. The system of claim 3, wherein each of the second identifierscomprises the MAC address for the RG, a Customer VLAN (C-VLAN) ID thatcorresponds to one of the hosts, and a Service VLAN (S-VLAN) ID thatcorresponds to one of the SPs, and wherein the second identifiers aremaintained in a second list at the AN.
 5. The system of claim 4, whereineach VLAN ID for each host in the first list is mapped to a C-VLAN IDand S-VLAN ID pair in the second list.
 6. The system of claim 4, whereinthe MAC address for the RG and each VLAN ID that corresponds to one ofthe hosts in the first list is associated with a port ID thatcorresponds to the access line in a third list that is maintained at theAN.
 7. The system of claim 6, wherein the first identifiers comprise aplurality of MAC addresses for a plurality of RGs, and wherein thesecond identifiers comprise the same MAC addresses.
 8. The system ofclaim 7, wherein each VLAN ID for each host that is associated with oneof the MAC addresses for the RGs in the first list is mapped to a C-VLANID and S-VLAN ID pair that corresponds to the same RG MAC address in thesecond list.
 9. The system of claim 8, wherein the third list comprise aplurality of port IDs for a plurality of access lines that correspond tothe RGs.
 10. A network component comprising: at least one processorconfigured to implement a method comprising: receiving a packet for aservice on a connection between a subscriber and a service provider(SP); replacing a Virtual Local Area Network (VLAN) tag for thesubscriber in the packet with a Customer VLAN (C-VLAN)/Service VLAN(S-VLAN) tag for the subscriber and the SP that matches a Media AccessControl (MAC) address for a router gateway (RG) in the packet if thepacket is received from the RG; and replacing a C-VLAN/S-VLAN tag forthe subscriber and the SP in the packet with a VLAN tag for thesubscriber that matches the MAC address for the RG in the packet if thepacket is received from the SP.
 11. The network component of claim 10,wherein the method further comprises: forwarding the packet to the SP ona connection indicated by the C-VLAN/S-VLAN tag if the packet isreceived from the RG; and forwarding the packet to the subscriber on aconnection indicated by the VLAN tag if the packet is received from theSP.
 12. The network component of claim 10, wherein the VLAN tag isassociated with the MAC address for the RG in a first list of accessnetwork connection identifiers, and wherein the C-VLAN/S-VLAN label isassociated with the same MAC address for the RG in a second list of SPnetwork connection identifiers.
 13. The network component of claim 10,wherein the packet is a router solicitation (RS) message.
 14. Thenetwork component of claim 10, wherein the packet is a Dynamic HostConfiguration Protocol (DHCP) message.
 15. The network component ofclaim 10, where the packet is forwarded at the network link layer. 16.The network component of claim 10, where the packet is forwarded withoutprocessing an Internet Protocol (IP) address in the packet.
 17. A methodcomprising: receiving from a host an authentication request for aVirtual Local Area Network (VLAN) connection to the host; receiving aCustomer VLAN (C-VLAN)/Service VLAN (S-VLAN) label for the host and aservice provider (SP) upon authentication of the VLAN, and associatingthe VLAN and the C-VLAN/S-VLAN label with a Media Access Control (MAC)address for a router gateway (RG) between the host and the SP.
 18. Themethod of claim 17 further comprising: receiving a router solicitation(RS) message from the RG on behalf of the host that requests routinginformation; and sending a routing acknowledgement (RA) message to theRG that comprises a prefix assigned to the host.
 19. The method of claim18, wherein the RS and RA messages indicate the VLAN but do not comprisea source Internet Protocol (IP) address for the RG.
 20. The method ofclaim 18, wherein the RS and RA messages indicate the VLAN and comprisean unspecified Internet Protocol (IP) address.